Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1479

reference: 170-tree-1
name: 1479
tree-preservation-order: undefined
170-tpo-1
uprn
address-text
point: POINT (-0.940551 50.862907)
geometry: MULTIPOLYGON (((-0.940495 50.862901,-0.940497 50.862912,-0.940505 50.862922,-0.940517 50.862930,-0.940533 50.862935,-0.940551 50.862937,-0.940568 50.862936,-0.940584 50.862931,-0.940597 50.862923,-0.940605 50.862913,-0.940608 50.862902,-0.940606 50.862891,-0.940598 50.862880,-0.940585 50.862872,-0.940570 50.862867,-0.940552 50.862865,-0.940535 50.862867,-0.940519 50.862872,-0.940506 50.862880,-0.940498 50.862890,-0.940495 50.862901)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL